Minutes, IBIS Quality Teleconference
July 30, 11 AM EST (8 AM PST)

- Roll call
Adam Tambone Adam.Tambone@fairchildsemi.com
*Barry Katz bkatz@sisoft.com
Benjamin P Silva benjamin.p.silva@intel.com
Bob Ross bob_ross@mentor.org
Eckhard Lenski Eckhard.Lenski@icn.siemens.de
*Eric Brock ebrock@sisoft.com
*Gregory R Edlund gedlund@us.ibm.com
Hazem Hegazy hazem_hegazy@mentorg.com
John Figueroa jfigueroa@apple.com
*Katta Koller (Siemens)
*Kevin Fisher kfisher@sisoft.com
*Kim Helliwell kimgh@apple.com
*Lynne Green lgreen@cadence.com
Mike Labonte mlabonte@hhnetwrk.com
Peter LaFlamme plaflamm@amcc.com
*Robert Haller rhaller@sisoft.com
*Roy Leventhal Roy_Leventhal@3com.com
Sherif Hammad sherif_hammad@mentorg.com
*Todd Westerhoff twesterh@cisco.com
Tom Dagostino tom_dagostino@mentorg.com

Everyone in attendance marked by  *

Interested, but have not yet attended:
    Ralf Bruening Zuken ralf.bruening@zuken.de
    Yabu Akira Elpida yabu-akira@elpida.com
    Jun Kitano Elpida jun.kitano@us.elpida.com


- Review of minutes for July 16
* Approved as written

- AR review
      AR: Barry to bring checklist up to date, based on past minutes.  =
DONE
by Eric Brock.
      AR: Lynne and Barry to identify Level 0 keywords. DONE.

- Opens for new items
* Updated keyword checklist posted.  IBIS 4 keywords added at bottom of
list for tracking.
* Possible new checklist items: Errors and Warnings produced by tool XX.
(Example: messages in ibis2signoise.)   Purely informational, based on
what is seen while verifying a model in an EDA tool.  This is in =
addition to
documentation for ibischk, which is already covered.  Documents what
model developer saw from one EDA tool, does not necessarily
relate to other EDA tools.  Might get unwieldy?  Might imply every EDA
tool needs a section?
Consensus: Provide a place to document EDA tool Errors and Warnings for
"Tool XX".
* Password to IBIS quality web site is the same as username.

- Level 0 keywords and required tool support.
* Level 0 has been discussed as passing the IBIS parser; something that
can be checked by software.  Example: should include Vinh and Vinl,
since default values not applicable for most logic today.
..What about programmable parts?  - Nothing we add at Level 0.
..Maybe require Ramp and V-t curves to be consistent, at least with the
same Rloads?
..Check combined curves before checking (non-monotonic, I-V vs. V-t,
Ramp, etc.)?
..Check for double-counting of clamps.
..For driver buffers, standard load timing, make Vref/Rref/Cref =
required.
Require at least one of the 3.  If Rref, also Vref.  Make Vmeas =
required.

* Should bring issues for parser forward to IBIS Open Forum soon, since
RFQ for new 4.0 parser will go out soon.  BIRDs are: (I-V combined =
before
performing monotonic checks and VT curve consistency, check for
double-counting of clamps,  adding standard load requirements, Check
consistency between RAMP and VT data when Rload =3D Rfixture).  Bob
Haller will get the form and file the first one.  Greg Edlund and Roy
Leventhal will also help.

* Brief discussion: Making it easy to generate a pinlist for a
field-programmable part.

- Next meeting agenda items
..Clarifying the checklist for "new" model makers, starting =
documentation.
..October release requirements.

- Schedule next meeting
August 13, 11 AM EST (8 AM PST)
Phone: 408-974-8478 or 800-249-5618
Meeting access: CONFERENCE SERVER 2, Conference ID: 4203

Meeting ended at 12:00 EST (9:00 AM PST).